Context Sensitive Framework For Providing Data From Relevant Applications

ABSTRACT

Functionality is disclosed herein for using a context sensitive framework to identify relevant applications to a current context and to provide data received from the relevant applications to a user. Instead of a user having to manually locate and launch an application, relevant applications determined by a contextual service may provide data in response to receiving the context data. The applications that are identified as relevant to the context determine the application data to provide to the contextual service. The contextual service selects at least a portion of the application data to provide for display within a user interface. In some configurations, the selected application data is displayed within a user interface that maintains a same look and feel regardless of the application data that is displayed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/623,875 filed on Feb. 17, 2015, the disclosure of which is herebyincorporated by reference in its entirety.

BACKGROUND

These days there are a large number of software applications that areavailable to users of mobile computing devices. For instance, someelectronic marketplaces include over a million different applications.Many of these applications are available free of charge or at a low costas compared to traditional desktop software applications. A user mightobtain applications by wirelessly connecting to the electronicmarketplace, browsing the available applications, and downloadingselected applications.

Trying to find applications among the millions of availableapplications, however, can be challenging for a user. For example, itmay be difficult for a user to decide on a particular application todownload, as there may be hundreds of available applications thatprovide the same or similar functionality. A user might look at customerratings for help in determining what applications to obtain. The usermight also download and try out applications. For example, some usersdownload hundreds of applications to their mobile computing device. Evenafter installing an application on the mobile computing device, however,the user might not always remember that the application is available foruse. Further, after installing an application, the user may still needto find the application on their device and launch the application whenthey want to use the application.

It is with respect to these and other considerations that the disclosuremade herein is presented.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting an illustrative operatingenvironment in which applications relevant to a current context providedata to a user;

FIG. 2 is a screen diagram showing an illustrative graphical userinterface (“GUI”) that displays application data received from differentapplications;

FIG. 3 is a system diagram that illustrates applications using acontextual service for communication;

FIG. 4 is a system diagram that illustrates identifying and utilizing anapplication to perform functionality in response to a current context ofa user;

FIG. 5 is a screen diagram showing an illustrative GUI that displaysanalytics relating to a use of one or more applications within thecontext sensitive framework;

FIG. 6 is a flow diagram showing a routine illustrating aspects of amechanism disclosed herein for selecting applications and organizingdata received from the selected applications using a context associatedwith a user;

FIG. 7 is a flow diagram showing a routine illustrating aspects of amechanism disclosed herein for registering applications with acontextual service;

FIG. 8 is a flow diagram showing a routine illustrating aspects of amechanism disclosed herein for providing access to an application thatis not currently available on a computing device associated with a user;

FIG. 9 is a flow diagram showing a routine illustrating aspects of amechanism disclosed herein for providing access to an application thatis not available on a computing device associated with a user;

FIG. 10 is a flow diagram showing a routine illustrating aspects of amechanism disclosed herein for applications to communicate with eachother using the contextual service;

FIG. 11 is a flow diagram showing a routine illustrating aspects of amechanism disclosed herein for selecting application data to provide tothe computing device that is associated with the user;

FIG. 12 is a system and network diagram that shows one illustrativeoperating environment for the examples disclosed herein that includes aservice provider network;

FIG. 13 is a computing system diagram that illustrates one configurationfor a data center that implements aspects of a service provider network,including some or all of the concepts and technologies disclosed hereinin which applications relevant to a current context provide data to auser; and

FIG. 14 is a computer architecture diagram showing one illustrativecomputer hardware architecture for implementing a computing device thatmight be utilized to implement aspects of the various examples presentedherein.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The following detailed description is directed to technologies for usinga context sensitive framework to identify relevant applications, such asend-user programs or operating system software, to a current context andto provide data received from the relevant applications. For example,the data might be provided for a user for display and/or to anotherapplication or computing device for some other use (e.g., performfunctionality using the current context). Through an implementation ofthe technologies disclosed herein, instead of a user having to manuallylocate and launch an application, relevant application data may beprovided in response to receiving context data that identifies a currentcontext of the user. As used herein, the term “context” may refer to thebackground, environment, framework, setting or situation that surroundsa particular event or situation. Generally speaking, the term“application” may refer to any set of program instructions or data aprocessor reads to perform some task or operation. In some examples, anapplication may be part of the system software (e.g., the operatingsystem) or might be application software (e.g., end-user programs).Context data might include location data, movement data, activity data,user data, time data, and the like. Some of the context data might bedetermined from sensors associated with a computing device. For example,the sensors of the computing device might be used to determine a speedof the computing device, a location of the computing device, weatherconditions, lighting conditions, sound near the user, facial expressionsof the user (or some other individual), and the like. The context datamight also include data relating to a current activity. For example, acurrent activity might relate to a user performing a search on thecomputing device, a user driving a car, a user accessing a particularwebsite, a user entering a restaurant, and the like.

A contextual service uses the context data to identify applications thatare relevant to the context. As used herein, the term “relevant” mayrefer to an application that provides data and/or functionality that isapplicable to the current context. An application may be determined tobe relevant for a particular context using registration data. Accordingto some configurations, applications and/or computing devices registerwith the contextual service to receive notifications, or be activated,in response to the contextual service receiving specified context data.In some configurations, applications or computing devices may receivethe context data without registering. As an example of using contextdata, fitness applications may be activated when the context dataindicates that the user is walking or jogging, global positioning system(“GPS”) applications may be activated when the context data indicatesthat the user is moving (e.g., driving) or the user is at a locationthat might utilize GPS (e.g., a golf course). Similarly, car rentalapplications might be activated when the context data indicates that theuser is located in an airport, is making a flight reservation, or isperforming a search for rental cars. In other examples, a computingdevice might be activated and/or be configured to perform some action inresponse to receiving context data. For instance, a thermostat might beconfigured to change a temperature setting in response to receivingcontext data indicating that the user is coming home. As othernon-exhaustive examples, context data can include any information about:location (such as obtained from GPS, Bluetooth, Bluetooth LE, RF, or anyother applicable location sensor), time, date, what application the useris using, what features the user is using on a particular application,physical environment (such as temperature, altitude, humidity, biometricpressure) device orientation, the proximity of other devices withrelevant data (such as a beacon or friend with a suitable device), theproximity of other users, biometric data (such as pulse, heart ratevariability, blood oxygenation, body temperature, blood sugar, sleep,what the user is viewing), and the like.

In response to being activated, the activated applications determine thedata to provide that is relevant to the context. In other words, theapplications use context data associated with a user to determine and toprovide application data that is personalized for the current context.As such, rather than a user having to determine what applications toutilize, the context sensitive framework uses the current context of auser in determining what applications to utilize. In this way, the userdoes not have to specifically locate and launch an application. In someexamples, the context sensitive framework receives application data frommore than one application, aggregates the application data, and providesthe application data for use. For example, selected application datamight be presented in a user interface. For instance, the contextsensitive framework may provide a common user interface for dataprovided by the different applications. In this way, the user ispresented with data from different applications in a consistent manner.In addition, this common user-interface may be provided as a part of theoperating system, thus allowing the interface of the operating system tochange as the context data changes.

The contextual service might also make a determination as to which dataprovided by different applications is to be provided. For instance, thecontextual service may de-duplicate data that overlaps (e.g., is thesame or similar) that is provided by different applications. Thecontextual service might also filter out data based on the currentcontext of the user.

The context of the user or a computing device may also be updated. Forexample, the computing device may periodically connect with thecontextual service to provide further or updated context data to thecontextual service. As the context of the user or computing devicechanges, the applications that were previously determined to be relevantmay change. For example, an application that was relevant for onecontext may not be relevant to an updated context. As such, thecontextual service may update the applications determined to be relevantin response to changes in context.

In other examples, the context sensitive framework may present the userwith a selection of different applications that are relevant to thecurrent context. For example, the context sensitive framework maypresent the user with the applications that registered to be activatedin response to the current context. After receiving a selection of anapplication from the user (e.g., through the common UI), the contextsensitive framework might launch the application for the user. In someexamples, the contextual service may also use temporal data whenselecting the applications that are relevant to the context. Forinstance, when it has been determined that a user has recently eaten,the contextual service may not utilize applications relating torestaurants for some period of time.

In other examples, when the application is not installed on thecomputing device being utilized by the user, the context sensitiveframework might cause the application to be installed on the computingdevice or might execute the application remotely, such as within aservice provider network. In some examples, the determination of whetherto install the application on the computing device of the user may bebased on whether it is likely that the user will frequently use theapplication. In some instances, an application may be downloaded to thecomputing device, installed on the computing device and thenautomatically removed after some period of time. For example, anapplication that was installed on the computing device may beautomatically removed after the context changes and/or the event forwhich the application was downloaded ends.

As briefly described, the context sensitive framework provides two-waycommunication between applications and the context sensitive framework.According to some configurations, the context sensitive framework allowstwo or more applications to communicate with each other. For example, anapplication may define a custom event using a contextual serviceapplication programming interface (“API”) to which other applicationsmay register to receive. Applications may use the custom event to senddata to other interested applications. For instance, a travelapplication may define a custom event that provides travel details for auser. This information might also be used to update the context datareceived by an application such that the data provided by theapplication is more applicable to the current context.

In some examples, a mobile computing device is configured to monitor thecontext of the user and to provide the context data to the contextualservice. In some cases, the context data is provided to the contextualservice when a network connection is established between the mobilecomputing device and a remote computing device that is part of thecontextual service. Periodically, or in response to a change in contextor some other trigger, the context data for the user is provided to thecontextual service. The contextual service may be implemented on thecomputing device and/or within a service provided by one or remotecomputers. In some examples, the contextual service is provided by anetwork-based service (e.g., a service provider network).

Software developers may develop applications using a software developertoolkit (“SDK”) that may include an API that specifies functionality forconnecting the application to a contextual service or other tools thatmight be used by a software developer to develop an application. Forexample, the contextual service API may be used by the application toregister to be activated or notified in response to one or morecontexts. The application might also utilize the API to define one ormore custom events, send a message to another application, request toreceive context data from a computing device, and the like. The SDKand/or API might also be utilized to change the operation of theoperating system and/or some other application. For instance, one partof the operating system might utilize the API to communicate withanother part of the operating system in response to receiving certaincontext data or application data.

Analytics may also be provided to an authorized user, such as a softwaredeveloper of applications, that relate to the use of the applications bythe contextual service. For example, the analytics might be displayed ina graphical user interface (“GUI”) and include information such as, butnot limited to usage data (e.g., average use), revenue data (e.g.,purchases, cost for usage), functionality utilized within theapplication, and the like. The user may view the analytics to determinehow applications are being utilized within the context sensitiveframework.

According to some configurations, the contextual service may collect andstore data that may be used to improve the recommendations and/or thedata provided by the contextual service. The data that may be collectedand stored may include context data received from different users and/orcomputing devices, application data received from various applications,and usage data associated with users of the contextual service. Forexample, the usage data might include what applications are selected bythe users, what applications are utilized by the users, as well as howthe users utilize the functionality of the application for differentcontexts. In some examples, the contextual service may use a machinelearning mechanism to improve the recommendations provided by thecontextual service. For instance, over time as the contextual servicereceives more data, the data provided by the contextual service maychange based on actual usage data associated with users of thecontextual service that is received. The machine learning mechanism maybe refined in response to receiving additional data. Additional detailsregarding the various components and processes described above forselecting and utilizing applications based on context will be presentedbelow with regard to FIGS. 1-14.

It should be appreciated that the subject matter presented herein may beimplemented as a computer process, a computer-controlled apparatus, acomputing system, or an article of manufacture, such as acomputer-readable storage medium. While the subject matter describedherein is presented in the general context of program modules thatexecute on one or more computing devices, those skilled in the art willrecognize that other implementations may be performed in combinationwith other types of program modules. Generally, program modules includeroutines, programs, components, data structures and other types ofstructures that perform particular tasks or implement particularabstract data types.

Those skilled in the art will also appreciate that aspects of thesubject matter described herein may be practiced on or in conjunctionwith other computer system configurations beyond those described herein,including multiprocessor systems, microprocessor-based or programmableconsumer electronics, minicomputers, mainframe computers, handheldcomputers, personal digital assistants, e-readers, mobile telephonedevices, tablet computing devices, special-purposed hardware devices,network appliances and the like. As mentioned briefly above, theexamples described herein may be practiced in distributed computingenvironments, where tasks may be performed by remote computing devicesthat are linked through a communications network. In a distributedcomputing environment, program modules may be located in both local andremote memory storage devices.

In the following detailed description, references are made to theaccompanying drawings that form a part hereof, and that show, by way ofillustration, specific examples or examples. The drawings herein are notdrawn to scale. Like numerals represent like elements throughout theseveral figures (which may be referred to herein as a “FIG.” or“FIGS.”).

Referring now to FIG. 1, an operating environment 100 is illustrated inwhich applications relevant to a current context provide data to a user,according to various examples presented herein. The operatingenvironment 100 shown in FIG. 1 includes computing devices 102A-102B, acontextual service 104, an application service 106, and an applicationexecution service 108.

According to some configurations, the computing devices 102A-102B, whichmay be referred to as “computing devices 102”, may each be configured asa tablet computing device, a smart phone, a personal computer (“PC”), adesktop computer, a laptop computer, a notebook computer, other mobilecomputing devices, a video game system, a set-top box, a smarttelevision, or the like. According to other examples, at least a portionof the functionality of the computing devices 102 may be provided by theapplication service 106, the application execution service 108, or aservice provider network 110 (See the service provider network 110illustrated in FIG. 12).

The contextual service 104, the application service 106, the applicationexecution service 108 or the service provider network 110 may includeone or more application servers, Web servers, data storage systems,network appliances, dedicated hardware devices, and/or other servercomputers or computing devices for providing the functionality of thedifferent services. In these examples, the computing devices 102 caninclude minimal hardware for connection to a network-based computingplatform via a network (not shown). The computing devices 102 maycommunicate via the network to access various services or computingresources described herein. For example, the computing devices 102 canaccess the contextual service 104, the application service 106 and/orthe application execution service 108. More details regarding theoperation of the contextual service 104, the application service 106,and the application execution service 108 are provided below.

The computing device 102A can be configured to execute an operatingsystem 112, applications 114, a contextual service API 116, as well asother application programs or components. The applications 114 mightinclude Web browser applications, productivity applications (e.g., wordprocessing, spreadsheet, and/or presentation applications), travelapplications, fitness applications, restaurant applications, socialnetwork applications, or any other applications. In some examples, oneor more of the applications 114 may be configured to utilize thecontextual service API 116. According to some configurations, theapplications might be part of the operating system 112 and/or some othercomponent. Although the computing device 102B is not shown in the samedetail as the computing device 102A, it should be understood that thecomputing device 102B, as well as other computing devices, may beidentically configured or may have more or fewer application programsand/or components than are illustrated for the computing device 102A.

The application service 106 may be configured to provide support for thecontextual service 104. For example, as discussed in more detail below,the contextual service 104 may utilize the application service 106 toobtain one or more applications 114 that are relevant to a currentcontext associated with a user (e.g., the user 120A or 120B).

Input to the applications 114 may be provided via one or more inputdevices that are connected to or otherwise are in communication with thecomputing device 102A. Input to the applications 114 can be used tocontrol aspects of the application 114, such as navigating menus. Thecomputing device 102A may also be configured to present the visualcontent provided by one or more applications 114 on one or more displaydevices that are built-in to or are external to and in communicationwith the computing device 102A, such as a display 122A.

The display 122A is an output device configured to present informationin a visual form. In particular, the display 122A may present visualcontent provided by the contextual service 104, the client contextmanager 124B, an application 114, and the like. The visual content mightinclude GUI elements, text, images, video, notifications, virtualbuttons, virtual keyboards, messaging data, Internet content, devicestatus, time, date, calendar data, preferences, map information,location information, and any other information that is capable of beingpresented in a visual form. In some examples, the display 122A is aliquid crystal display (“LCD”) utilizing any active or passive matrixtechnology and any backlighting technology (if used). In other examples,the display 122A may be an organic light emitting diode (“OLED”)display. Other display types are contemplated. In addition, the display122A can include an input device such as a touchscreen or multi-touchenabled touchscreen.

All or a portion of the applications 114 may utilize a contextualservice API 116 to interact with the contextual service 104, theapplication service 106 and/or the application execution service 108. Asdiscussed above, the applications 114 might be any instructions or datathat provide one or more functions. The applications 114 may beconfigured to call one or more methods exposed by the contextual serviceAPI 116 to access the contextual service 104 via a network to takeadvantage of one or more of the features provided by the contextualservice 104. The applications 114 can also be configured to call one ormore methods exposed by the contextual service API 116 to access theapplication service 106 or the application execution service 108. Forexample, the contextual service API 116 may be used by one or more ofthe applications 114 to register to receive notifications, and possiblybe activated, in response to a current context of the user 120A. Thecontextual service API 116 might also be used to send data to anotherapplication 114, request data relating to a current context, and thelike.

A user 120A may interact with the contextual service 104 using thecomputing device 102A. In some examples, the UI 130A that is displayedon the display 122A may be used to view and interact with the contextualservice 104.

As illustrated, the contextual service 104 includes the context manager124A that manages one or more sessions during which a computing device,such as the computing device 102A, interacts with the contextual service104. The contextual service 104 may support connections to any number ofcomputing devices 102 so that one or more users utilizing the variouscomputing devices 102 can share data with the contextual service 104,the application service 106, the application execution service 108, andpossibly with one another. As such, the illustrated example is merelyillustrative, and should not be construed as being limiting in any way.

In the current example illustrated in FIG. 1, a context sensitiveframework that includes the contextual service 104 identifiesapplications 114 that are relevant to a current context of a user (e.g.,the user 120A or 120B) and provides application data 118 received fromthe relevant applications 114 to the user. As briefly discussed above,instead of a user having to manually locate and launch an application114, the relevant applications 114 to a current context of the user mayprovide application data 118 that is relevant to the current context ofthe user.

In order to determine a current context for a user, the client contextmanager 124 might utilize one or more of the sensors 126 of thecomputing device 102A. The sensors 126 might be configured to determineat least a portion of the context data 128A. For examples, the sensors126 might determine location data, movement data (e.g., speed oracceleration data), weather data, biometric data, time data, lightingdata, facial recognition data, and the like. Some of the context data128A that is associated with a current context of the user 120A might bedetermined from the current activity of the computing device 102A. Forexample, a current activity might relate to a user performing a search,a user launching an application, a user accessing a website, and thelike. In some examples, the client context manager 124B aggregates thevarious data relating to the current context and sends the context data128A to the contextual service 104.

The contextual service 104 uses the received context data 128A toidentify one or more applications 114 that are relevant to the currentcontext of the user 120A. As briefly discussed above, an application 114may be determined to be relevant for a particular context based, atleast in part, on whether the application 114 registered with thecontextual service 104 to be activated in response to a current contextindicated by the context data 128. For example, the contextual service104 may determine that the applications 114A-114F are relevant to thecontext specified by the context data 128A. The applications 114determined to be relevant may or may not be installed on the computingdevice 102A. In the current example, the applications 114A-114C areinstalled on the computing device 102A and the applications 114D-114Fare located remotely (e.g., within the application service 106 and/orthe application execution service 108).

According to some configurations, applications 114, register with thecontextual service 104 to be activated in response to the contextualservice 104 receiving a specified context data 128A. For example,fitness applications may register with the contextual service 104 to beactivated when the context data 128A indicates that the user is walkingor jogging. Other applications 114 may be activated when the contextdata 128A indicates that the user is moving. Similarly, car rentalapplications 114 might be activated when the context data 128A indicatesthat the user 120A is located in an airport, is making a flightreservation, or is performing a search for rental cars. In otherexamples, the contextual service 104 may determine the applications 114to activate.

In response to being activated, the activated applications, such as theapplications 114A-118F, determine the application data 118A-118F toprovide to the contextual service 104 and/or the client context manager124B or the context manager 124A that is relevant to the context data128A. In other words, the relevant applications that are activated bythe contextual service 104 and/or the client context manager 124B, usethe context data 128A to determine the application data 118A to provide.For example, a sports application 114 that is determined to be relevantmay provide different application data 118 before a football game (e.g.,pregame data) as compared to during a football game (e.g., currentscore, current stats for the game). Instead of the contextual service104 requesting specify application data 118 from an application 114, thecontextual service 104 is configured to activate the application 114 andprovide the application 114 with the context data 128A. In someexamples, the contextual service 104 might also request specific datafrom one or more of the relevant applications 114A-114F. As discussed inmore detail below, the applications 114A-114F may be executed on thecomputing device 102A and/or within the application execution service108, or on some other computing device.

As illustrated, rather than the user 120A or 120B having to determinewhat applications 114 to utilize, the context sensitive framework thatincludes the contextual service 104 uses the current context of a userin determining the applications to utilize. In this way, the user doesnot have to specifically locate and launch an application 114.

In some examples, the context sensitive framework receives applicationdata 118 from more than one application, aggregates the application data118, and presents selected application data 118 in a user interface 130,such as the user interface 130A or 130B. For instance, the contextsensitive framework may provide a common user interface, which may be apart of the operating system software, to present the application data118A-118F provided by the different applications 114A-114F. In this way,the user is presented with data from different applications in aconsistent manner.

The contextual service 104 might also make a determination as to whichapplication data 118 received from the different applications 114A-114Fis to be provided to the user. For instance, the contextual service 104may remove the duplicate data (or similar data) from the applicationdata 118A-118F. The contextual service 104 and/or the client contextmanager 124B might also filter out data based on the current context ofthe user.

In other examples, the contextual service 104 may determine what othercomputing devices 102 and/or other applications are to receive theapplication data 118. For instance, the contextual service 104 mightprovide the application data 118 to other computing devices within ahome of the user in response to determining that the user is either athome, or is traveling home and will arrive within a specified period oftime. As another example, the contextual service 104 might provide theapplication data 118 to other computing devices, such as those in a carin order to start the car, in response to determining that the user isabout to get in the car. This could also include loading mapping ordirections software with the user's likely destination, as well asproviding traffic-related information.

The context data 128 associated with the user 120A may also updated withthe contextual service 104. For example, the computing device 102A mayconnect with the contextual service 104 to provide further or updatedcontext data 128A to the contextual service 104. As the context data128A associated with the current context of the user changes (e.g., thelocation of the user changes), the applications 114A-114F that werepreviously determined to be relevant may no longer be determined to berelevant. For example, an application that was relevant for one contextmay not be relevant to an updated context. As such, the contextualservice 104 may update the relevant applications in response to changesin context.

In other examples, the context sensitive framework may present the userwith a selection of different applications that are relevant to thecurrent context. For example, the contextual service 104 may present theuser 120B with a selection of applications 114 that registered to beactivated in response to the current context. After receiving aselection of an application from the user, such as through the UI 130B,the contextual service 104 might cause the selected application 114G tobe launched. In some configurations, the selected application 114G mightbe launched within the application execution service 108. In otherconfigurations, the selected application 114G may be launched on thecomputing device 102B.

When the selected application 114G is not installed on the computingdevice 102B being utilized by the user, the contextual service 104 mightcause the application 114G to be installed on the computing device 102B.In some examples, the determination of whether to install theapplication 114G on the computing device 102B may be based on aprediction of how often the user 120B might use the application 114G.For example, in some cases a selected application 114G might only beutilized once (e.g., an application for a specific event). In someinstances, the client context manager 124C may connect to the electronicmarketplace 132, download the application 114G to the computing device102B, and cause the application 114G to be installed on the computingdevice 102B. After installation of the application 114G, the clientcontext manager 124C may launch the application 114G and then, possibly,at some later point automatically remove the application 114G from thecomputing device 102B. For example, the application 114G might beremoved after an event the application 114G has completed (e.g. after afew hours, a few day, or the like). For instance, if a user is going toa football game, the application 114G may be automatically downloaded,then removed once that user has left the football game.

When the application execution service 108 executes the selectedapplication 114G (or some other remote computing device) the contextmanager 124A of the contextual service 104 may provide the applicationdata 118G generated the by application 114G to the client contextmanager 124C. The application data 118G might be the application data118G that is relevant to the context data 128B or might be some otherportion or all of the data generated by the application 114G.

As briefly described above, the context sensitive framework providestwo-way communication between applications 114 and the contextualservice 104. According to some configurations, the context sensitiveframework allows two or more applications 114 to communicate with eachother. More details for two or more applications 114 using the contextsensitive framework to communicate are provided below with regard toFIG. 2.

In some examples, the client context manager 124B or 124C is configuredto monitor the context of the user and to provide the context data 128Aor 128B to the contextual service 104. In some cases, the context data128 is provided to the contextual service 104 when a network connectionis established between the computing device 102 and a remote computingdevice that is part of the contextual service 104.

In some examples, software developers may develop applications 114 usinga software developer toolkit (“SDK”) that may include an applicationprogramming interface (“API”), such as the contextual service API 116,that specifies functionality for connecting the application 114 to thecontextual service 104 or other tools that might be used by a softwaredeveloper to develop an application. For example, the contextual serviceAPI 116 may be used by the application to register to be activated ornotified in response to one or more contexts. The application 114 mightalso utilize the contextual service API 116 to define one or more customevents that may be used to communicate data to another application 114and/or to the contextual service 104.

As briefly discussed above, the contextual service 104 may collect andstore data, such as in the data store 134A, that may be used to improvethe recommendations, such as the identifying data 136 and/or theapplication data 118A-118F that is provided by the contextual service.The data that may be collected and stored by the contextual service 104may include the context data 128 received from different users and/orcomputing devices, application data 118 received from variousapplications, and usage data associated with users of the contextualservice. For example, the usage data might include what applications areselected by the users, what applications are utilized by the users, aswell as how the users utilize the functionality of the application fordifferent contexts.

In some configurations, the contextual service 104 may use a machinelearning mechanism to improve the recommendations provided by thecontextual service. The term “machine learning” may refer to one or moreprograms that learns from the data it receives. For example, a machinelearning mechanism may build, modify or otherwise utilize a model thatis created from example inputs and makes predictions or decisions usingthe model. In the current example, the machine learning mechanism may beused to improve the identification applications 114 that are dataprovided by the contextual service 104. The model may be trained usingsupervised and/or unsupervised learning. For instance, over time as thecontextual service receives more data, the data provided by thecontextual service may change based on actual usage data associated withusers of the contextual service that is received. The machine learningmechanism utilized by the contextual service 104 may be refined inresponse to receiving additional data

Analytics may also be provided to a software provider, or some otherauthorized user, that relate to the use of the applications 114 by oneor more users utilizing the context sensitive framework. For example,the analytics might be displayed in a GUI and include information suchas, but not limited to usage data (e.g., average use), revenue data(e.g., purchases, cost for usage), functionality utilized within theapplication, and the like. The software provider may view the analyticsto determine how their applications are being utilized within thecontext sensitive framework. FIG. 5 illustrates an exemplary GUI 500that may be used to provide the analytics.

In some examples, the application service 106 provides the electronicmarketplace 132 through which users can purchase content, such as, forexample, the applications 114, application add-ons, in-applicationitems, music, e-books, movies, and the like. It should be understoodthat various implementations of the operating environment 100 includemultiple networks, contextual services 104, application services 106,application execution services 108, applications 114 and contextualservice APIs 116. As such, the illustrated operating environment 100should be understood as being illustrative, and should not be construedas being limiting in any way.

FIG. 2 is a screen diagram showing an illustrative GUI 200 that displaysapplication data 118 received from different applications 114. GUI 200could be part of an end-user program or the operating system of thecomputing device, or a combination thereof. As illustrated, the GUI 200shows data from different applications that are relevant to a currentcontext of a user, such as the user 120A or 120B. The computing device102A that is in communication with the contextual service 104 mightdisplay the GUI 200. For purposes of explanation, and not intended to belimiting, assume that the GUI 200 is being used by a user that iscurrently at a SEATTLE SEAHAWKS football game. For instance, the contextdata 128 may indicate that the user is located in the sports stadiumwhere the Seattle Seahawks play.

As discussed above, one or more applications 114 may provide applicationdata 118 to the contextual service 104 in response to being activated.In response to receiving the context data 128 that is associated withthe user that is at the football game, the contextual service 104 hasidentified a Seahawks application 114H, a stadium application 114I, ageneral sports application 114J, a weather application 114K, and a foodapplication 114L that are relevant to the context data 128. The usermight select or deselect the applications 114 to utilize by selecting auser interface element within the select application UI element 206. Asdiscussed above, a user might not choose to receive data from all theapplications determined to be relevant to the context data 128. In thisexample, the user has decided not to include the use of the foodapplication 114L as indicated by the dashed line around the foodapplication 114L. In some examples, the selections received from theuser may be provided to the contextual service 104 and used to updatethe model utilized by the machine learning mechanism. In this way, theapplications identified to be relevant to a certain context may changeover time in response to the selections made by the users of thecontextual service.

In the current example, the GUI 200 shows application data 118H-118Kfrom a portion of the applications 114H-114L identified to be relevantto the current context. The GUI 200 shows the application data withinthe selected application data UI element 202. The GUI 200 also showsuser interface elements that are associated with the selectedapplications 114-114L within the user interface elements section 204.The user interface elements section 204 shows the user interfaceelements for the Seahawks application UI 204A, the stadium applicationUI 204B, the general sports application UI 204C, and the weatherapplication UI 204D. As can be seen, each of the applications UI204A-204D includes the options 1-N. In some examples, the user interfaceelements 204 for the different applications 114H-114K may be combined orotherwise displayed in a different manner.

As discussed above, the application data 118 that is displayed withinthe GUI 200 may be selected, at least in part, by the applicationproviding the application data 118 to the contextual service 104. Inother words, instead of requesting specific information from theapplications, the contextual service 104 receives application data 118from the applications that the application determines to be relevant tothe context data 128. For example, the Seahawks application 114H mightinclude pre-game information before the game is started, scores andstats for a game while the game is in progress and post-game analysisand reviews after the game. As the context data 128 changes (e.g., thetime changes during the game), each of the applications 114H-114K mayupdate the application data 118H-118K that is provided to the contextualservice, 104. As discussed above, the contextual service 104 may use amachine learning mechanism when determining what application data toprovide.

In some examples, a user might be able to launch an individualapplication from within the GUI 200. For example, the user might selectan option (not shown) within the UI elements shown for the particularapplication. In other examples, a user might also be able to customizethe GUI 200. For instance, in response to selecting a customize UIelement (not shown), a user may then be prompted to select the differentinformation that they would like to include in the display of the GUI200. For example, a user may select from a list (or some other UIelement or input method) the application data 118 that they would likedisplayed as well as how the data is displayed.

FIG. 3 is a system diagram 300 that illustrates applications 114 usingthe contextual service 104 for communication. System diagram 300includes the contextual service 104 in communication with theapplication execution service 108. The contextual service 104 mayinclude the context manager 124A, the data store 134A, and a reportingcomponent 302. The application execution service 108 may include one ormore computing devices for executing the applications 114A-114N. Inother examples, all or a portion of the applications 114A-114N may beexecuted on the computing device 102A, or some other computing device.

The applications 114A-114N may be configured to send and receive datato/from the contextual service 104. The applications 114A-114N may alsoutilize the contextual service 104 and the contextual service API 116 tocommunicate with each other. For example, an application, such as theapplication 114A may generate the application data 118A in response toreceiving the context data 128A. In some examples, all or a portion ofthe application data 118A may be provided by the contextual service 104to one or more of the other applications, such as the application 114B.The application data 118A might be provided directly to the application114B as indicated by the dashed line or indirectly to the application114B through the context manager 124A.

As discussed above, an application 114, such as the application 114A,may specify one or more custom events to be utilized by the contextualservice 104 using the contextual service API 116. For example, thecustom events might relate to application data that is provided by theapplication 114A that other applications might be interested inreceiving. For example, the Seahawks application 114H illustrated inFIG. 2 might specify a custom event that provides data about the SEATTLESEAHAWKS that is not generally available to the other applications. Inorder to receive the application data 118A that is associated with thecustom event specified by the application 114A, the application 114B mayregister to receive notifications relating to one or more custom eventsspecified by the applications 114. In other examples, an application,such as the application 114A might utilize functionality provided by thecontextual service API 116 to directly send direct data 304 to anotherapplication, such as the application 114B.

In some examples, the application 114B receiving the direct data 304and/or the application data 118A from the application 114A may use thedata to generate the application data 118B that is provided to thecontext manager 124A that is part of the contextual service 104. Inother configurations, the context manager 124A may use the receivedapplication data 118A to update the context data 128A. For example, insome cases, the application data 118A might include additional contextdata 128 that may be used to update the context that is associated withthe user of the computing device 102A. The context manager 124A mightprovide the updated context data 128C to all or a portion of theapplications 114A-114N. In the current example, the context manager 124Ahas provided the updated context data 128C to the application 114N. Theapplication 114N uses the updated context data 128C to generate theapplication data 118N.

The reporting component 302 may be configured to provide analytics. Forexample, the analytics reporting component 302 included in thecontextual service 104 may be configured to provide the GUI 500illustrated in FIG. 5, that displays analytics relating to a user of oneor more of the applications 114A-114N. The analytics may be displayed onthe UI 130A that is associated with the computing device 102A that maybe utilized by a software provider, or some other authorized user. Thereporting component 302 may also be configured to create reports thatinclude information relating to one or more of the applications114A-114N (e.g., configuration information).

FIG. 4 is a system diagram 400 that illustrates identifying andutilizing an application 114 to perform functionality in response to acurrent context of a user. System diagram 400 includes the contextualservice 104, the application service 106, and the computing device 102B.As discussed above, in some cases, an application 114G identified asbeing relevant to a current context may be downloaded to the computingdevice 102B.

According to some configurations, the contextual service 104 receivesthe context data 128B associated with the user 120B and the contextmanager 124A determines the applications 114 that are relevant to thecontext. The context manager 124A might determine the relevantapplications 114 from the registered applications 402 that areregistered with the contextual service 104. The context manager 124Amight also determine the relevant applications 114 from applications 114that are not registered with the contextual service 104. For example,the context manager 124A might determine the relevant applications 114from the applications available from the electronic marketplace 132. Insome instances, the context manager 124 uses data available from theelectronic marketplace 132, or some other source, to determinefunctionality and/or the popularity of an application.

In the current example, the context manager 124A identifies the relevantapplications 404 that are relevant to the context data 128B. Forexample, the relevant applications 404 might be the applications 114that registered to be activated in response to the context data 128B. Insome configurations, the context manager 124A may select one of therelevant applications 404 to provide to the computing device 102B inresponse to the context data 128B. In other examples, the contextmanager 124A may present the user with a selection of differentapplications that are relevant to the current context. For example, thecontextual service 104 may provide relevant application data 406 to bepresented in the user interface 130B. In the current example, the user120B selects the application 114G to be utilized. After receiving aselection of the application 114G from the user 120B, the contextualservice 104 might cause the selected application 114G to be downloadedto the computing device 102B.

As discussed above, the determination of whether to install theapplication 114G on the computing device 102B may be based on aprediction of how often the user 120B might use the application 114G.For example, in some cases a selected application 114G might only beutilized once (e.g., an application for a specific event). In someinstances, the client context manager 124C may connect to the electronicmarketplace 132, download the application 114G to the computing device102B, and cause the application 114G to be installed on the computingdevice 102B. After installation of the application 114G, the clientcontext manager 124C may launch the application 114G and then, possibly,at some later point automatically remove the application 114G from thecomputing device 102B. For example, the application 114G might beremoved after an event the application 114G has completed (e.g. after afew hours, a few day, or the like).

FIG. 5 is a screen diagram showing an illustrative GUI 500 that displaysanalytics relating to a use of one or more applications within thecontext sensitive framework. As illustrated in the applications section504, the GUI 500 shows analytics relating to the applications 114H-114Killustrated in FIG. 2. The data presented in the GUI 500 might bedetermined by a computing device associated with the contextual service104, the application service 106, or some other computing device. TheGUI 500 may be presented on a computing device, such as the computingdevice 102B.

For purposes of explanation, and not intended to be limiting, assumethat the GUI 500 is being used by a developer of the contextual service104 to view analytics relating to the use of one or more of theapplications 114 that were utilized during a particular time period orwith a particular context. The GUI 500 might display a variety ofdifferent analytics and UI elements. In the current example, the GUI 500shows a configuration UI element 502A, a type of use UI element 502B, anaverage usage UI element 502C, a revenue UI element 502D, and aconversion rate 502E. In the current example, the currently selectedapplication is the stadium application 114I as indicated by the boldeddashed line displayed around the stadium application UI element.

The configuration UI element 502A may display configuration informationrelating to the stadium application 114I. The types of use UI element502B may display data indicating how the application is used. In thecurrent example, the types of use UI element 502B indicates that thescore functionality of the stadium application 114I was used 22% of thetime and the stats functionality of the stadium application 114I wasused 58% of the time. In some configurations (not shown) a user mightselect one or more options that specify to display data that isassociated with one or more users. For instance, a user might specify tosee analytics on how an application is used in the context of a footballgame by a single user or a group of users. In other examples, a usermight specify to see analytics on how the application is used by usersnot attending a sporting event. The average usage UI element 502C maydisplay an average number of hours that the stadium application 114I isused during a time period (e.g., daily, weekly, monthly). In the currentexample, the average usage UI element 502C is configured to display anumber of hours for average weekly use by a customer. In other examples,the average usage UI element 502C might be configured to display howmuch the application is used in other contexts. The revenue UI element502D may display an average revenue generated during a specified timeperiod. In the current example, the revenue UI element 502D shows anamount of revenue generated during one week. The conversion UI element502E may display the average conversion rate for an application that maybe presented to a user for use.

In some examples, all or a portion of the different UI elements might beselected to obtain additional information or configure differentoptions. A user might select one of the UI elements shown in theapplications section 504 to change the currently selected application.

A user might also be able to customize the GUI 500 by selecting thecustomize UI element 502F. In response to selecting the customize UIelement 502F, a user may then be prompted to select the differentinformation that they would like to include in the display of the GUI500. For example, a user may select from a list (or some other UIelement or input method) the analytics that they would like displayed.In another example, the user may select how the plan analytics is to bedisplayed. For example, the user may request to have the plan analyticsdisplayed as raw data, as a graphical representation (e.g., tables,charts, graphs), or in some other format. A user may also request tohave historical information displayed in the GUI 500. For example, auser may request to see a time series display of the usage of theapplication, or some other data.

The information presented in the GUI 500 might also be downloaded forlater use. As illustrated, a user may select the download UI element502G to download the information to a local data store, a network datastore, or to another location. The analytics may be downloaded in one ormore formats. For example, a user may download all or a portion of thecustomer support information as a text file, a spreadsheet file, aword-processing file, or some other file.

FIGS. 6-11 are flow diagrams showing routines that illustrate aspects ofusing a context sensitive framework to identify relevant applications toa current context and to provide data received from the relevantapplications to a user according to an example disclosed herein. Itshould be appreciated that the logical operations described herein withrespect to FIGS. 6-11, and the other FIGS., may be implemented (1) as asequence of computer implemented acts or program modules running on acomputing system and/or (2) as interconnected machine logic circuits orcircuit modules within the computing system.

The implementation of the various components described herein is amatter of choice dependent on the performance and other requirements ofthe computing system. Accordingly, the logical operations describedherein are referred to variously as operations, structural devices,acts, or modules. These operations, structural devices, acts, andmodules may be implemented in software, in firmware, in special purposedigital logic and any combination thereof. It should also be appreciatedthat more or fewer operations may be performed than shown in the FIGS.and described herein. These operations may also be performed inparallel, or in a different order than those described herein.

FIG. 6 is a flow diagram showing a routine 600 illustrating aspects of amechanism disclosed herein for selecting applications and organizingdata received from the selected applications using a context associatedwith a user. The routine 600 may begin at 602, where context data 128 isobtained that is associated with a user. As discussed above, the contextdata 128 may be obtained by a client context manager 124 operating on acomputing device 102 that is associated with a user. The context data128 may include various context data, such as but not limited to acurrent time of day, a current location of the user, weather data, whatactions are being performed on the computing device 102, and the like.

At 604, the context data 128 is provided to the contextual service. Asdiscussed above, the context data 128 may be provided by the clientcontext manager 124 operating on the computing device 102 to thecontextual service 104 or might be provided using some other mechanism.In some examples, the context data 128 is provided to the contextualservice 104 and may be updated periodically, or in response to someevent or condition. In other examples, the context data 128 might beprovided to the contextual service 104 when a network connection isestablished, and/or at periodic times.

At 606, data is received that identifies relevant applications toutilize. As discussed above, the data that is received may includeidentifying data 136 that identifies the relevant applications 114. Inother examples, the data might include the application itself or thedata might include application data 118 provided by the one or more ofthe applications 114.

At 608, the context data 128 is provided to the applications 114identified to be relevant. As discussed above, context data 128 might beprovided to all or a portion of the applications 114 identified to berelevant. In some examples, the contextual manager 124 operating withinthe contextual service 104 identifies the most relevant applications 114and provides the context data 128 received from the computing device 102to those applications 114.

At 610, application data 118 is received from the applications 114. Asdiscussed above, the application data 118 that is received may beselected by the applications 114 themselves. Instead of the contextmanager 124 requesting specific types of data from an application 114,the contextual service 104 allows the application 114 to select theapplication data 118 to provide based on the context data 128 providedthe computing device 102.

At 612, the application data 118 to provide to is selected. As discussedabove, the application data 118 received from the relevant applications114 might include duplicate data as well as other data that might not berelevant to the current context. In some examples, the context manager124 removes duplicate data from the application data 118, prioritizesportions of the application data 118 and formats the application data118 to be provided. In some examples, the application data 118 isformatted to be provided to the user. In other examples, the applicationdata 118 is formatted to be provided to another application and/orcomputing device 102.

At 614, the selected data is provided. As discussed above, the selecteddata may be provided in a user interface 130 that provides a common UIregardless of what applications are being utilized by the contextualservice 104. In other examples, the user interface 130 may be the nativeinterface provided by the application 114 or the applications 114 thatare relevant to the context data 128. In other examples, the selecteddata is provided in a format useable by the computing device 102.

FIG. 7 is a flow diagram showing a routine 700 illustrating aspects of amechanism disclosed herein for registering applications 114 with acontextual service 104. At 702, applications 114 may be configured toutilize the contextual service API 116. As discussed above, anapplication 114 may utilize the contextual service API 116 that providesfunctionality to register with the contextual service 104. For example,an application 114 may register to be activated for various contexts asspecified by the context data 128. The applications 114 might also beconfigured to utilize other functionality of the contextual service API116, such as defining custom events, communicating with otherapplications 114, and the like. As discussed above, the applications 114may be associated with a computing device, such as, but not limited to athermostat, a thermostat, lighting system, alarm system, car,dishwasher, washing machine, dryer, refrigerator, oven, some other homeautomation system, and the like. For examples, a lighting device mayutilize the API to communciate with the contextual service 104. In someconfigurations, the applications 114 may be implemented as a system on achip (“SOC”) and may utilize functionality provided by the API.

At 704, the applications 114 register with the contextual service 104.As discussed above, different applications 114 may register with thecontextual service 104 to be activated in response to different contextsthat may be associated with a user. Some applications 114 may registerto be activated in response to one or more different conditions (e.g.,specified location at a specified time). As discussed above, in someconfigurations, the contextual service 104 may provide data tounregistered applications.

At 706, the contextual service registers the applications. As discussedabove, after receiving a registration request, the contextual service104 registers the applications such that the registered applications areactivated in response to the specified conditions.

FIG. 8 is a flow diagram showing a routine 800 illustrating aspects of amechanism disclosed herein for providing access to an application thatis not currently available on a computing device associated with a user.The routine 800 may begin at 802, where context data 128 is received. Asdiscussed above, the context data 128 may be received by the contextmanager 124A operating within the contextual service 104.

At 804, the application to utilize is determined. As discussed above,the contextual service 104 may be used to determine one or moreapplications 114 that might be utilized by the user associated with thecontext data 128. In some configurations, the contextual service 104presents the UI 130 to a user with the applications 114 that haveregistered for the context data 128. The UI 130 may then be used by theuser to receive a selection of at least one of the applications 114 tobe utilized. In other examples, the UI 130 may not be presented toreceive a selection of an application 114. For instance, the contextualservice 104 may select one or more of the applications 114 using thecontext manager 124A. As discussed above, the context manager 124A maypredict whether an application is likely to be utilized by the userusing a machine learning mechanism, or some other mechanism. At 806, theapplication 114 is installed on the computing device 102 whendetermined. As discussed above, the application 114 may be installed onthe computing device 102 when the selected application is currently notavailable on the computing device.

At 808, the application 114 is activated. As discussed above, the clientcontext manager 124 may cause the application 114 to be activated on acomputing device 102. In some examples, the application 114 might belaunched on the computing device 102 for use by the user. In otherexamples, the application 114 might be launched and run on a remotecomputing device in a service provider network, with the applicationdata being streamed to the user device.

At 810, the application 114 may be removed from the computing device 102when determined. As discussed above, the application 114 might beremoved when a determination is made by the contextual service 104 thatthe application 114 is not likely to be utilized by the user 120 in thefuture. In some cases, the application is removed after some period oftime or in response to some other condition (e.g., after the contextchanges).

FIG. 9 is a flow diagram showing a routine 900 illustrating aspects of amechanism disclosed herein for providing access to an application thatis not available on a computing device associated with a user. Theroutine 900 may begin at 902, where the context data 128 is received. Asdiscussed above, the context data 128 may be received by the contextmanager 124A operating within the contextual service 104.

At 904, the application to utilize is determined. As discussed above,the contextual service 104 may be used to determine one or moreapplications 114 that might be utilized by the user associated with thecontext data 128. In some configurations, the contextual service 104presents the UI 130 to a user with the applications 114 that haveregistered for the context data 128. In other examples, the contextualservice 104 uses the context data 128 to determine relevant applications114 that are available from the electronic marketplace 132. The UI 130may then be used by the user to receive a selection of at least one ofthe applications 114 to be utilized.

At 906, the application 114 is activated. As discussed above, theapplication 114 may be executed within the application execution service108, or on some other computing device.

At 908, the application data 118 is provided. As discussed above, thecontext manager 124A may provide the application data 118 received fromthe application execution service 108 to the client context manager 124operating on the computing device 102. The application data 118 might beprovided to the user or used by some other application or computingdevice 102, such as a smart thermostat, lighting system, alarm system,car, dishwasher, washing machine, dryer, refrigerator, oven, some otherhome automation system, and the like.

FIG. 10 is a flow diagram showing a routine 1000 illustrating aspects ofa mechanism disclosed herein for applications to communicate with eachother using the contextual service. The routine 1000 may begin at 1002,where application data 118 is received from a first application. Asdiscussed above, applications 114 may utilize the contextual service API116 to register custom events with the contextual service 104. Otherapplications 114 may register to receive notifications associated withan occurrence of a custom event defined by the first application.

At 1004, the received application data 118 may be used to update thecontext data 128. As discussed above, the application data 118 receivedfrom the first application 114 may provide additional contextualinformation relating to the current context. In some examples, theapplication data 118 received from the first application may not berelated to the current context. In this case, the contextual service 104does not update the context data 128.

At 1006, the application data 118 received from the first applicationand/or the updated context data is provided to one or more otherapplications 114. As discussed above, the contextual service 104 mayprovide at least a portion of the application data 118 that is relatedto the custom event to the applications 114 that registered to receivenotifications of the custom event. In some configurations, thecontextual service 104 provides the updated context data 128 to each ofthe other applications 114 that are relevant to the current context. Asalso discussed, the application data 118 might be provided to anothercomputing device and used to control an operation of that device. Forinstance, the application data 118 may be provided to a thermostat andused by the application 114 utilized by the thermostat to change atemperature setting.

At 1008, updated application data 118 is received from the otherapplications. As discussed above, the applications determine what datato provide to the contextual service 104. As such, the updated contextdata 128 provided by the contextual service 104 may cause theapplication 114 to provide different application data 118. In someexamples, the updated context data 128 may be received from anothercomputing device, such as from a thermostat, lighting system, alarmsystem, car, dishwasher, washing machine, dryer, refrigerator, oven,some other home automation system, and the like.

FIG. 11 is a flow diagram showing a routine 1100 illustrating aspects ofa mechanism disclosed herein for selecting application data to provideto the computing device that is associated with the user. The routine1100 may begin at 1102, where application data 118 is received fromapplications 114. As discussed above, the application data 118 that isreceived from the different applications is selected and chosen by theapplication 114 providing the data. This is in contrast to merelyrequesting specific data from the application.

At 1104, the application data 118 to provide to the user may be selectedusing customer preferences. As discussed above, the customer preferencesmay be determined from preferences specified in one or more customerprofiles or might be determined from historical data associated with theuser. For example, it may be determined that the user has previouslyselected certain application data 118, or another application 114, overother application data 118 or other applications 114. The customerpreferences might also be determined from explicit settings that may belocated within a customer profile, or some other memory.

At 1106, the duplicate data from the selected application data 118 isremoved. As discussed above, the application data 118 that is receivedfrom the different applications may include data that is duplicated oris similar to each other.

At 1108, the application data is formatted for display in the userinterface. As discussed above, the context manager may format the datato be provided within a common user interface 130 such that users arenot distracted by the use of different user interfaces associated witheach of the different applications.

FIG. 12 and the following description are intended to provide a brief,general description of a suitable computing environment in which theexamples described herein may be implemented. In particular, FIG. 12 isa system and network diagram that shows an illustrative operatingenvironment that includes a service provider network 110. As discussedabove, service provider network 110 can provide virtual machineinstances and computing resources on a permanent or an as-needed basis.

The computing resources provided by the service provider network 110 mayinclude various types of resources, such as data processing resources,data storage resources, networking resources, data communicationresources and the like. Each type of computing resource may begeneral-purpose or may be available in a number of specificconfigurations. For example, and as will be described in greater detailbelow, data processing resources may be available as virtual machineinstances in a number of different configurations. The virtual machineinstances may be configured to execute applications, including Webservers, application servers, media servers, database servers and othertypes of applications. Data storage resources may include file storagedevices, block storage devices and the like. Each type or configurationof a virtual machine instance of a computing resource may be availablein different sizes, such as large resources, consisting of manyprocessors, large amounts of memory, and/or large storage capacity, andsmall resources consisting of fewer processors, smaller amounts ofmemory and/or smaller storage capacity.

The computing resources provided by service provider network 110 areenabled in one implementation by one or more data centers 1204A-1204N(which may be referred to herein singularly as “a data center 1204” orcollectively as “the data centers 1204”). The data centers 1204 arefacilities utilized to house and operate computer systems and associatedcomponents. The data centers 1204 typically include redundant and backuppower, communications, cooling and security systems. The data centers1204 might also be located in geographically disparate locations. Oneillustrative configuration for a data center 1204 that implements someor all of the concepts and technologies disclosed herein will bedescribed below with regard to FIG. 13.

The users and customers of service provider network 110 may access thecomputing resources provided by the data centers 1204 over a suitabledata communications network, such as a Wide Area Network (“WAN”), asillustrated by network 1230. Although a WAN might be used, it should beappreciated that a local-area network (“LAN”), the Internet, or anyother networking topology known in the art that connects the datacenters 1204 to the computing devices 102 may be utilized. It shouldalso be appreciated that combinations of such networks might also beutilized.

FIG. 13 is a computing system diagram that illustrates one configurationfor a data center 1204 that implements aspects of a service providernetwork 110, including some or all of the concepts and technologiesdisclosed herein in which a context sensitive framework is used toidentify relevant applications to a current context and to provide datareceived from the relevant applications to a user. The example datacenter 1204 shown in FIG. 13 includes several server computers1302A-1302F (which may be referred to herein singularly as “a servercomputer 1302” or in the plural as “the server computers 1302”) forproviding computing resources. The server computers 1302 may be standardtower or rack-mount server computers configured appropriately forproviding the computing resources described herein. According to anexample, the server computers 1302 are configured to execute thesoftware products as described above.

In one example, some of the computing resources 1304 are virtual machineinstances. As known in the art, a virtual machine instance is aninstance of a software implementation of a machine (i.e. a computer)that executes programs like a physical machine. Each of the servercomputers 1302 may be configured to execute an instance manager (notshown) capable of instantiating and managing computing resources andinstances of computing resources. In the case of virtual machineinstances, for example, the instance manager might be a hypervisor oranother type of program configured to enable the execution of multiplevirtual machine instances on a single server computer 1302, for example.

It should be appreciated that although the examples disclosed herein aredescribed primarily in the context of virtual machine instances, othertypes computing resources can be utilized with the concepts andtechnologies disclosed herein. For instance, the technologies disclosedherein might be utilized with hardware resources, data storageresources, data communications resources, networking resources, databaseresources and with other types of computing resources.

The data center 1204 shown in FIG. 13 also includes a server computer1302F reserved for executing software components for managing theoperation of the data center 1204, the server computers 1302, virtualmachine instances, and other resources within the service providernetwork 110. The server computer 1302F might also execute the contextmanager 124A and include the data store 134A. Details regarding theoperation of each of these components has been provided above. In thisregard, it should be appreciated that while these components areillustrated as executing within service provider network 110, computingsystems that are external to service provider network 110 might also beutilized to execute some or all of these components. Otherconfigurations might also be utilized.

In the example data center 1204 shown in FIG. 13, an appropriate localarea network (“LAN”) 1305 is utilized to interconnect the servercomputers 1302A-1302E and the server computer 1302F. The LAN 1305 isalso connected to the network 1230 illustrated in FIG. 12. It should beappreciated that the configuration and network topology illustrated inFIGS. 12 and 13 has been greatly simplified and that many more computingsystems, networks and networking devices may be utilized to interconnectthe various computing systems disclosed herein. Appropriate loadbalancing devices or software modules might also be utilized forbalancing a load between each of the data centers 1204A-1204N, betweeneach of the server computers 1302A-1302F in each data center 1204 andbetween virtual machine instances and other types of computing resourcesprovided by the service provider network 110.

It should be appreciated that the data center 1204 described in FIG. 13is merely illustrative and that other implementations might also beutilized. Additionally, it should be appreciated that the functionalityprovided by these components might be implemented in software, hardware,or a combination of software and hardware. Other implementations shouldbe apparent to those skilled in the art.

FIG. 14 shows an example computer architecture for a computer 1400capable of executing program components for using a context sensitiveframework to provide application data to a user in the manner describedabove. The computer architecture shown in FIG. 14 illustrates aconventional server computer, workstation, desktop computer, laptop,tablet, network appliance, personal digital assistant (“PDA”), e-reader,digital cellular phone, or other computing device, and may be utilizedto execute any of the software components presented herein. For example,the computer architecture shown in FIG. 14 may be utilized to executesoftware components for performing operations as described above. Thecomputer architecture shown in FIG. 14 might also be utilized toimplement a computing device 102, a computing device utilized in thecontextual service 104, the application service 106 or the applicationexecution service 108 or any other of the computing systems describedherein.

The computer 1400 includes a baseboard 1402, or “motherboard,” which isa printed circuit board to which a multitude of components or devicesmay be connected by way of a system bus or other electricalcommunication paths. In one illustrative example, one or more centralprocessing units (“CPUs”) 1404 operate in conjunction with a chipset1406. The CPUs 1404 may be standard programmable processors that performarithmetic and logical operations necessary for the operation of thecomputer 1400.

The CPUs 1404 perform operations by transitioning from one discrete,physical state to the next through the manipulation of switchingelements that differentiate between and change these states. Switchingelements may generally include electronic circuits that maintain one oftwo binary states, such as flip-flops and electronic circuits thatprovide an output state based on the logical combination of the statesof one or more other switching elements, such as logic gates. Thesebasic switching elements may be combined to create more complex logiccircuits, including registers, adders-subtractors, arithmetic logicunits, floating-point units and the like.

The chipset 1406 provides an interface between the CPUs 1404 and theremainder of the components and devices on the baseboard 1402. Thechipset 1406 may provide an interface to a RAM 1408, used as the mainmemory in the computer 1400. The chipset 1406 may further provide aninterface to a computer-readable storage medium such as a read-onlymemory (“ROM”) 1410 or non-volatile RAM (“NVRAM”) for storing basicroutines that help to startup the computer 1400 and to transferinformation between the various components and devices. The ROM 1410 orNVRAM may also store other software components necessary for theoperation of the computer 1400 in accordance with the examples describedherein.

The computer 1400 may operate in a networked environment using logicalconnections to remote computing devices and computer systems through anetwork, such as the local area network 1420. The chipset 1406 mayinclude functionality for providing network connectivity through anetwork interface controller (“NIC”) 1412, such as a gigabit Ethernetadapter. The NIC 1412 is capable of connecting the computer 1400 toother computing devices over the local area network 1420. It should beappreciated that multiple NICs 1412 may be present in the computer 1400,connecting the computer to other types of networks and remote computersystems.

The computer 1400 may be connected to a data store, such as the datastore 134, that provides non-volatile storage for the computer. The datastore 134 may store system programs, application programs, other programmodules and data, which have been described in greater detail herein.The data store 134 may be connected to the computer 1400 through astorage controller 1414 connected to the chipset 1406. The data store134 may consist of one or more physical storage units. The storagecontroller 1414 may interface with the physical storage units through aserial attached SCSI (“SAS”) interface, a serial advanced technologyattachment (“SATA”) interface, a fiber channel (“FC”) interface, orother type of interface for physically connecting and transferring databetween computers and physical storage units.

The computer 1400 may store data on the data store 134 by transformingthe physical state of the physical storage units to reflect theinformation being stored. The specific transformation of physical statemay depend on various factors, in different implementations of thisdescription. Examples of such factors may include, but are not limitedto, the technology used to implement the physical storage units, whetherthe data store 134 is characterized as primary or secondary storage andthe like.

For example, the computer 1400 may store information to the data store134 by issuing instructions through the storage controller 1414 to alterthe magnetic characteristics of a particular location within a magneticdisk drive unit, the reflective or refractive characteristics of aparticular location in an optical storage unit, or the electricalcharacteristics of a particular capacitor, transistor, or other discretecomponent in a solid-state storage unit. Other transformations ofphysical media are possible without departing from the scope and spiritof the present description, with the foregoing examples provided only tofacilitate this description. The computer 1400 may further readinformation from the data store 134 by detecting the physical states orcharacteristics of one or more particular locations within the physicalstorage units.

In addition to the data store 134 described above, the computer 1400 mayhave access to other computer-readable storage media to store andretrieve information, such as program modules, data structures, or otherdata. It should be appreciated by those skilled in the art thatcomputer-readable storage media is any available media that provides forthe non-transitory storage of data and that may be accessed by thecomputer 1400.

By way of example, and not limitation, computer-readable storage mediamay include volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology. Computer-readable storage mediaincludes, but is not limited to, RAM, ROM, erasable programmable ROM(“EPROM”), electrically-erasable programmable ROM (“EEPROM”), flashmemory or other solid-state memory technology, compact disc ROM(“CD-ROM”), digital versatile disk (“DVD”), high definition DVD(“HD-DVD”), BLU-RAY, or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium that can be used to store the desired information ina non-transitory fashion.

The data store 134 may store an operating system 1430 utilized tocontrol the operation of the computer 1400. According to one example,the operating system comprises the LINUX operating system. According toanother example, the operating system comprises the WINDOWS® SERVERoperating system from MICROSOFT Corporation. According to furtherexamples, the operating system may comprise the UNIX operating system orthe ANDROID operating system. It should be appreciated that otheroperating systems may also be utilized. The data store 134 may storeother system or application programs and data utilized by the computer1400, such as components that include the context manager 124, theapplication 114 and/or any of the other software components and datadescribed above. The data store 134 might also store other programs anddata not specifically identified herein.

In one example, the data store 134 or other computer-readable storagemedia is encoded with computer-executable instructions which, whenloaded into the computer 1400, transform the computer from ageneral-purpose computing system into a special-purpose computer capableof implementing the examples described herein. These computer-executableinstructions transform the computer 1400 by specifying how the CPUs 1404transition between states, as described above. According to one example,the computer 1400 has access to computer-readable storage media storingcomputer-executable instructions which, when executed by the computer1400, perform the various routines described above with regard to FIGS.6-11. The computer 1400 might also include computer-readable storagemedia for performing any of the other computer-implemented operationsdescribed herein.

The computer 1400 may also include one or more input/output controllers1416 for receiving and processing input from a number of input devices,such as a keyboard, a mouse, a touchpad, a touch screen, an electronicstylus, or other type of input device. Similarly, the input/outputcontroller 1416 may provide output to a display, such as a computermonitor, a flat-panel display, a digital projector, a printer, aplotter, or other type of output device. It will be appreciated that thecomputer 1400 may not include all of the components shown in FIG. 14,may include other components that are not explicitly shown in FIG. 14,or may utilize an architecture completely different than that shown inFIG. 14.

Based on the foregoing, it should be appreciated that technologies forusing a context sensitive framework to identify relevant applications toa current context and to provide data received from the relevantapplications to a user have been presented herein. Moreover, althoughthe subject matter presented herein has been described in languagespecific to computer structural features, methodological acts andcomputer readable media, it is to be understood that the inventiondefined in the appended claims is not necessarily limited to thespecific features, acts, or media described herein. Rather, the specificfeatures, acts and media are disclosed as example forms of implementingthe claims.

The subject matter described above is provided by way of illustrationonly and should not be construed as limiting. Furthermore, the claimedsubject matter is not limited to implementations that solve any or alldisadvantages noted in any part of this disclosure. Variousmodifications and changes may be made to the subject matter describedherein without following the example examples and applicationsillustrated and described, and without departing from the true spiritand scope of the present invention, which is set forth in the followingclaims.

What is claimed is:
 1. A system comprising: one or more processors; and one or more memories to store a set of instructions, which if executed by the one or more processors, causes the one or more processors to perform operations comprising: sending, to a network-based contextual service, first data that includes context data associated with a user's use of a computer; receiving, from the network-based contextual service, second data identifying a plurality of applications determined by the contextual service to be relevant to a current context, the plurality of applications comprising a first application and a second application; obtaining third data from the first application and obtain fourth data from the second application; and providing at least a portion of the third data combined with at least a portion of the fourth data within a first section of a user interface.
 2. The system of claim 1, wherein the operations further comprise obtaining the context data from sensor data obtained from one or more sensors of the computer.
 3. The system of claim 1, wherein the operations further comprise obtaining one or more of the plurality of applications from an electronic marketplace to install the one or more of the applications on the computer.
 4. The system of claim 1, wherein the context data comprises one or more of a location of the computer, a time, or a current activity performed by the computer.
 5. The system of claim 1, wherein the user interface comprises a second section that includes first user interface elements associated with the first application and second user interface elements associated with the second application.
 6. The system of claim 1, wherein the operations further comprise updating the context data and sending, to the network-based contextual service, the updated context data.
 7. The system of claim 1, wherein the first application and the second application are executed in a service provider network.
 8. A method comprising: sending, to a network-based contextual service, first data that includes context data associated with a user's use of a computer; receiving, from the network-based contextual service, second data identifying a plurality of applications determined by the contextual service to be relevant to a current context, the plurality of applications comprising a first application and a second application; obtaining third data from the first application and obtain fourth data from the second application; and providing at least a portion of the third data combined with at least a portion of the fourth data within a first section of a user interface.
 9. The method of claim 8, further comprising obtaining the context data from sensor data obtained from one or more sensors of the computer.
 10. The method of claim 8, further comprising obtaining one or more of the plurality of applications from an electronic marketplace to install the one or more of the applications on the computer.
 11. The method of claim 8, wherein the context data comprises one or more of a location of the computer, a time, or a current activity performed by the computer.
 12. The method of claim 8, wherein the user interface comprises a second section that includes first user interface elements associated with the first application and second user interface elements associated with the second application.
 13. The method of claim 8, further comprising updating the context data and sending, to the network-based contextual service, the updated context data.
 14. The method of claim 8, wherein the first application and the second application are executed in a service provider network.
 15. A non-transitory computer-readable medium having stored thereon a set of instructions, which if performed by one or more processors, causes the one or more processors to perform operations comprising: sending, to a network-based contextual service, first data that includes context data associated with a user's use of a computer; receiving, from the network-based contextual service, second data identifying a plurality of applications determined by the contextual service to be relevant to a current context, the plurality of applications comprising a first application and a second application; obtaining third data from the first application and obtain fourth data from the second application; and providing at least a portion of the third data combined with at least a portion of the fourth data within a first section of a user interface.
 16. The non-transitory computer-readable medium of claim 15, wherein the operations further comprise obtaining the context data from sensor data obtained from one or more sensors of the computer.
 17. The non-transitory computer-readable medium of claim 15, wherein the operations further comprise obtaining one or more of the plurality of applications from an electronic marketplace to install the one or more of the applications on the computer.
 18. The non-transitory computer-readable medium of claim 15, wherein the context data comprises one or more of a location of the computer, a time, or a current activity performed by the computer.
 19. The non-transitory computer-readable medium of claim 15, wherein the user interface comprises a second section that includes first user interface elements associated with the first application and second user interface elements associated with the second application.
 20. The non-transitory computer-readable medium of claim 15, wherein the operations further comprise updating the context data and sending, to the network-based contextual service, the updated context data. 